questions:
what do we expect from the GUIs?
what functions should they provide?

GUIs from the Slow-Control Scheme:
first Web-GUIs then other graphical interfaces
For most Web-GUIs, there is already something existing, therefore we
discussed them less detailed.


quality display:
----------------
enhance by:
- general flag
- tool for plotting quality info vs time, run#, ... (more flexible
solution than plotdb.php)
other remarks:
- weatherinfo + other info not on runbasis should go to DB

runbook display:
----------------
- select type
- select severity

runbook insert:
---------------
- information to insert:
   * time stamp
   * user name
   * system
   * severity level
   pull down menus for the latter two
- types of runbook entries
   * automatic
   * operator
   * hw interaction
   * alarm message

alarm display:
--------------
apart from sms etc: include in runbook display


schedule gui:
-------------
two types of schedules:
   Meta Schedule: source, total # of hours
   Nightly Schedule: automaticall created by Autoschedule
- display schedules
- edit schedules (both meta and nightly)
- possibility to have fixed time windows for a source (eg MWL campaign)
   -> flag: manually/automatic
- information:
   * time
   * maybe time window
   * target
   * flag
questions that occured during discussion:
   maybe a DB with future runs?
   do we want to start runs through the web interface?
more detailed sketch and requirements for the autoscheduler will follow



other graphical interfaces:
---------------------------
in general:
- display information
- set configuration manually, eg for tests
- display values of whole night
   remark: might have impact on the data format choice
   (fits: one should not open files which are not yet closed
    what about crashes? can the files be repaired?)
- possibility to have several windows (maybe just start several
   displays)
- display-only mode, "login" to control telescope
- time-to-sunrise
- see IF there is an error
- possibility to start run
- normal operation: display of current operation + alerts in case of pb
- emergency button (visible always)
- nice-to-have: chat to communicate between users

possible layout attached
tabs to be displayed:
- rate control
- light censor?
- starguider?
- weather station?
- clound monitor?
- drive
- trigger
- daq/evtbuilder
- lv
- hv

general/run gui:
----------------
- start button + tell which system one wants to control with this
   button (configuration of other subsystems in the other tabs)
- reset-to-defaut button
- maybe: extra tab to start data taking and configure drive and trigger
question: can autoscheduler take care of thresholds?


drive:
------
- pointing position
- tpoint button
- view of telescope
- tabs to keep from magic drive display: insert, control deviation,
   telescope position, info

starguider?:
------------
- start/stop
- # correlated stars
- sky brightness?

bias voltage feedback:
----------------------
- set command values for gain
- display voltage command values of system (camera display)
- display calculated gain (camera display)
- display temporal developement (avg over camera vs time)
- difference between command and calculated values
- rms? differenc to avg of cam

lv control:
-----------
- on/off
- display
- vs time

lid:
----
- open/close
- display status

auxiliary:
----------
- camera temperature vs time (values of current night)
- humidity

bias voltage control:
---------------------
- set voltage values manually

event builder:
--------------
- start/stop
- event display
- pulse shape for one choosable pixel

daq control / trigger / calibration system:
-------------------------------------------
- trigger rate over time (possibility to zoom)
- trigger threshold (set and display)
- rates of sumpatches
- frequency of light pulsar
- rate of artificial events
- on/off
- # of time samples to readout (for testing phase)
- switch off pixels
- perscaling?

weather display:
----------------
- temperature
- humidity
- wind speed
- clouds?
